Maintaining minimum interface functionality in an absence of a push-based communications connection in a group-based communication system

ABSTRACT

Methods, systems, and apparatuses are provided for maintaining minimum interface functionality in an absence of a push based communications connection in a group-based communication system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation application claiming prioritybenefit, with regard to all common subject matter, of U.S. patentapplication Ser. No. 17/020,352, filed on Sep. 14, 2020 and entitled“MAINTAINING MINIMUM INTERFACE FUNCTIONALITY IN AN ABSENCE OF APUSH-BASED COMMUNICATIONS CONNECTION IN A GROUP-BASED COMMUNICATIONSYSTEM” (“the '352 application”). The ‘'352 application is acontinuation application claiming priority benefit, with regard to allcommon subject matter, of U.S. patent application Ser. No. 16/670,984,filed Oct. 31, 2019, and entitled “MAINTAINING MINIMUM INTERFACEFUNCTIONALITY IN AN ABSENCE OF A PUSH-BASED COMMUNICATIONS CONNECTION INA GROUP-BASED COMMUNICATION SYSTEM” (“the '984 application”). The '984application claims priority benefit, with regard to all common subjectmatter, of earlier-filed U.S. Provisional Patent Application No.62/755,691, filed Nov. 5, 2018, and entitled “MAINTAINING MINIMUMINTERFACE FUNCTIONALITY IN AN ABSENCE OF A PUSH-BASED COMMUNICATIONSCONNECTION IN A GROUP-BASED COMMUNICATION SYSTEM.” The identifiedearlier-filed patent applications are hereby incorporated by referencein their entirety into the present application.

BACKGROUND

Systems have been provided for interactions between client devices andservers over push-based communications connections. Through appliedeffort, ingenuity, and innovation many deficiencies of such systems havebeen solved by developing solutions that are in accordance with theembodiments of the present invention, many examples of which aredescribed in detail herein.

BRIEF SUMMARY

Various embodiments serve to provide a near real-time representation ofgroup-based communication interface objects at a client device despitean interruption in a real-time messaging communication connection (e.g.,an active websocket connection) to a group-based communication server.The various embodiments ensure a group-based communication interfacemaintains a minimum level of functionality or quality of service in theabsence of a real-time messaging communication connection. Thegroup-based communication server is associated with a remote computingplatform (such as a group-based communication platform or othercentralized data distribution computing platform). In embodiments,client devices subscribe to events associated with group-basedcommunication interface objects such that a group-based communicationserver configured for real-time messaging communications transmitsupdated object data associated with those group-based communicationinterface objects to which the client device has subscribed as soon asthe updated object data is available.

In addition to establishing the real-time messaging communicationconnection with a first group-based communication server, the clientdevice establishes a second communication connection with a differentgroup-based communication server (e.g., a web API) for polling torequest tail data payloads. Because a duration of any interruption inthe real-time messaging communication connection is unknown, it ispreferable for the client device to request more updated object datafrom the different group-based communication server than would havenormally been pushed to the client device, hence the request for thetail data payload. While the real-time messaging communicationconnection is maintained, tail data payloads are discarded.

However, in the event of an interruption in the real-time messagingcommunication connection between the client device and the group-basedcommunication server configured for real-time messaging communications,various embodiments provide for the use of all of or a part of a taildata payload to render a subsequent group-based communication interface.The subsequent group-based communication interface may support a minimumlevel of functionality using the tail data payload(s), as opposed tocompletely losing functionality in the absence of updated object data.The minimum level of functionality (or minimum interface functionality)may include the ability to send messages (i.e., transmit messages to agroup-based communication platform/system intended for display in aparticular group-based communication channel interface), readgroup-based communication channels (i.e., receive group-basedcommunication interfaces configured to render for display on the clientdevice group-based communication channel interfaces), and view unreadgroup-based communication channels (i.e., receive group-basedcommunication interfaces configured to render for display on the clientdevice group-based communication interfaces comprising digitalrepresentation of group-based communication channels having messagesassociated therewith that have not yet been accessed by the clientdevice).

In embodiments, an apparatus for maintaining minimum interfacefunctionality in a group-based communications system comprises at leastone processor and at least one non-transitory storage device storinginstructions that, when executed by the processor, cause the apparatusto receive user interaction input representative of electronicinteractions with group-based communication interface objects. Inembodiments, the electronic interactions with the group-basedcommunication interface objects require updated object data forrendering a subsequent group-based communications interface. Inembodiments, the electronic interactions are associated with one or moreobject identifiers.

In embodiments, the apparatus is further caused to establish a firstcommunications connection with a first remote server. In embodiments,the first remote server is configured for transmitting in real-timeupdated object data representative of events associated with group-basedcommunication interface objects to which the client device hassubscribed. In embodiments, the updated object data is pushed from thefirst remote server to the client device.

In embodiments, the apparatus is further caused to establish a secondcommunications connection with a second remote server. In embodiments,the second communications connection is a client-pull-basedcommunications connection and configured for requesting and receiving,by the client device, tail data payloads from the second remote server.

In embodiments, the apparatus is further caused to transmit a pollingrequest to the second remote server. In embodiments, the polling requestcomprises the one or more object identifiers. In embodiments, thepolling request is representative of a request for a tail data payloadfor each of the one or more object identifiers.

In embodiments, the apparatus is further caused to receive, from thesecond remote server, the tail data payloads for each of the one or moreobject identifiers.

In embodiments, the apparatus is further caused to query a local datastore of the client device for updated object data associated with theone or more object identifiers.

In embodiments, the apparatus is further caused to detect aninterruption in the first communications connection upon determining theupdated object data associated with the one or more object identifiersis not available in a local data store of the client device nor has theupdated object data associated with the one or more object identifiersbeen received from the first remote server.

In embodiments, the apparatus is further caused to render for displaythe subsequent group-based communications interface using a first taildata payload subset. In embodiments, the first tail data payload subsetis selected from the tail data payload based on the required updatedobject data associated with the electronic interactions.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 shows a schematic view of a group-based communication platform incommunication with client devices according to embodiments of thepresent disclosure;

FIG. 2A shows a schematic view of an apparatus for use with embodimentsof the present disclosure;

FIG. 2B shows a schematic view of a client device for use withembodiments of the present disclosure;

FIG. 3A shows a schematic view of data transmissions between a clientdevice and a group-based communication platform or system, according toembodiments of the present disclosure; and

FIG. 3B is a flowchart illustrating the data transmissions between theclient device and a group-based communication platform or system,according to embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure more fully describes various embodiments withreference to the accompanying drawings. It should be understood thatsome, but not all embodiments are shown and described herein. Indeed,the embodiments may take many different forms, and accordingly thisdisclosure should not be construed as limited to the embodiments setforth herein. Rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Like numbersrefer to like elements throughout.

Overview

In a group-based communication system, client devices receive datatransmissions from group-based communication servers and rendergroup-based communication interfaces based on the received data. Objectsassociated with the group-based communication interfaces, and thereforethe group-based communication system, may be rapidly changing, quicklyrendering any object data at the client device “stale” or “out of date.”Accordingly, a group-based communication system may rely upon areal-time messaging (RTM) communications connection to provide real-timeupdated object data to client devices based on objects for which eachclient device has requested updates.

In the event that real-time messaging communications connections areinterrupted for any reason, object data at the client device may remainstale or out of date, and the client device may not actively interactwith the group-based communication interface. Embodiments of the presentdisclosure provide a solution to this problem.

While polling by client devices in the group-based communication system,on a regular basis in place of a real-time messaging connection, may notprovide ideal performance (i.e., latency), polling presents a reliablebackup mechanism by which a client device may receive updated objectdata and support operations and interactions with the group-basedcommunication interface on the client device.

The inventors have determined that a sole reliance upon a real-timemessaging connection (e.g., an active websocket connection) for receiptby a client device of updated object data associated with a group-basedcommunication system leads to a lack of up to date object data on aclient device and a resulting compromise of application functionality(e.g., a group-based communication interface may not perform or functionas intended), reducing efficient use of computing resources by theclient device (i.e., excess stale data in cache/memory, excessiveinterface refreshes, improper allocation of screen real estate, and thelike).

Accordingly, presented herein are embodiments directed to a nearreal-time representation of group-based communication interface objectsat a client device despite an interruption in a real-time messagingcommunication connection (e.g., an active websocket connection) to agroup-based communication server. Embodiments comprise a detection of aninterruption in the real-time messaging communications connection upondetermining the updated object data associated with one or more objectidentifiers is not available in a local data store of the client devicenor has the updated object data associated with the one or more objectidentifiers been received from the first remote server. The clientdevice has also established a second communications connection with adifferent group-based communications server (e.g., via a web API) andrequested a tail data payload for each of the objects associated withthe one or more object identifiers. Under normal operating conditions,when the client device confirms that the updated object data isavailable in the local data store and/or that the updated object datahas been received from the first remote server, the client devicediscards the tail data payload.

In embodiments, upon determining that the real-time messagingcommunications connection is interrupted, and therefore that the updatedobject data has not been received over the real-time messagingcommunications connection, the client device uses (rather than discards)the tail data payload(s) to render a subsequent group-basedcommunication interface. It will be appreciated that the tail datapayload comprises more data than would have been received over thereal-time messaging communication connection (i.e., the updated objectdata pushed to the client device from the first remote server).

The client device can then render a subsequent group-based communicationinterface based on all of or a subset of the received tail datapayloads. Accordingly, the group-based communication interface mayprovide minimum functionality with near real-time updated object data.

Definitions

As used herein, the terms “data,” “content,” “information,” and similarterms may be used interchangeably to refer to data capable of beingtransmitted, received, and/or stored in accordance with embodiments ofthe present invention. Thus, use of any such terms should not be takento limit the spirit and scope of embodiments of the present invention.Further, where a computing device is described herein to receive datafrom another computing device, it will be appreciated that the data maybe received directly from another computing device or may be receivedindirectly via one or more intermediary computing devices, such as, forexample, one or more servers, relays, routers, network access points,base stations, hosts, and/or the like. Similarly, where a computingdevice is described herein to send data to another computing device, itwill be appreciated that the data may be sent directly to anothercomputing device or may be sent indirectly via one or more intermediarycomputing devices, such as, for example, one or more servers, relays,proxies, routers, network access points, base stations, hosts, and/orthe like.

The term “user” should be understood to refer to an individual, a groupof individuals, business, organization, and the like. Users may access agroup-based communication or messaging system using client devices.“Group-based” is used herein to refer to a system, channel, message, orvirtual environment that has security sufficient such that it isaccessible only to a defined group of users. The group may be defined bycommon access credentials such as those of an organization or commercialenterprise. Access may further be facilitated by a validated request tojoin or an invitation to join transmitted by one group member user toanother non-member user. Group identifiers (defined below) are used toassociate data, information, messages, etc., with specific groups.

The terms “user profile,” “user account,” and “user account details”refer to information associated with a user, including, for example, auser identifier, one or more communication channel identifiers (e.g.,group-based communication channel identifiers) associated withcommunication channels (e.g., group-based communication channels) thatthe user has been granted access to, one or more group identifiers forgroups with which the user is associated, an indication as to whetherthe user is an owner of any group-based communication channels, anindication as to whether the user has any group-based communicationchannel restrictions, a plurality of messages, a plurality of emojis, aplurality of conversations, a plurality of conversation topics, anavatar, an email address, a real name (e.g., John Doe), a username(e.g., jdoe), a password, a time zone, a status, and the like. The useraccount details can include a subset designation of user credentials,such as, for example, login information for the user including theuser's username and password.

The term “client device” refers to computer hardware(s) and/orsoftware(s) that is/are configured to access one or more services madeavailable by one or more servers. The server(s) is/are often (but notalways) on another computer system (e.g., a computing platform, such asa group-based communication platform), in which case the client deviceaccesses the service by way of a network. A client device may beassociated with a group identification, where the group identificationis an electronic indication that suggests a group (e.g., user group)that the user belongs to. Client devices may include, withoutlimitation, smart phones, tablet computers, laptop computers, desktopcomputers, wearable devices, personal computers, enterprise computers,and the like.

To access the services of a computing platform, the client device and/orcomputing platform establish a network connection (e.g., a“communication connection”) therebetween embodied as an individualconnection session. A single client device may utilize a plurality ofconnection sessions with a computing platform for data transfer over aperiod of time. As discussed herein, data relevant to a particularclient device (e.g., updates for particular objects) may continue to begenerated by (or provided to) the computing platform between connectionsessions (while the client device is disconnected from the computingplatform), and such data may be provided to the client device during asubsequent connection session.

In embodiments, a communication connection may be an active websocketconnection (e.g., an “real-time messaging” (RTM) connection, a “push” orserver initiated connection), a non-RTM connection (e.g., a “pull” orclient initiated connection), and the like. A client device maycommunicate with an RTM server (e.g., a group-based communication serverconfigured for real time messaging communications) over an activewebsocket connection. A client device may, in addition or alternatively,communicate with a non-RTM server (e.g., a group-based communicationserver not configured for real time messaging communications) over anon-RTM connection (e.g., by utilizing an HTTP request message).

The terms “group-based communication system” and “group-basedcommunication platform” refer to a communications software platform andassociated hardware that is configured to support and maintain aplurality of group-based communication interfaces and all associatedfunctionality. Group-based communication system users are organized intoorganization groups (e.g., employees of different companies may beseparate organization groups) and each group interacts with the systemvia a respective group-based communication interface. For example, thegroup-based communication system might support, among others, a SlackCorporation group-based communication interface and an ACME Corporationgroup-based communication interface. Example group-based communicationsystems comprise supporting servers, client devices, and externalapplication servers.

The term “group-based communication channel” refers to a virtualcommunications environment or feed that is configured to displaygroup-based messages posted by channel members (e.g., validated usersaccessing the environment using client devices) that are viewable onlyto the members of the group. The format of the group-based communicationchannel may appear differently to different members of the group-basedcommunication channel; however, the content of the group-basedcommunication channel (i.e., group-based messages) will be displayed toeach member of the group-based communication channel. For instance, acommon set of group-based messages will be displayed to each member ofthe respective group-based communication channel such that the contentof the group-based communication channel interface (i.e., group-basedmessages) will not vary per member of the group-based communicationchannel. In embodiments, however, the content of the group-basedcommunication channel interface may vary per member of the group-basedcommunication channel based on varying permissions associated with eachmember (e.g., a first member may post a message to a channel along witha file; the message may be displayed to a second member but the file maynot be accessible by the second member, in which case the display of thefile may differ from the display of the file to the first member).

Multiple communication channels may operate on each of one or morecomputing devices, and therefore a communication channel identifier maybe assigned to a communication channel, which indicates the physicaladdress in a database where related data of that communication channelis stored and which is utilized to identify client devices thatparticipate within the communication channel to receive data exchangedon the communication channel. The communication channel identifiertherefore ensures communication channels remain distinct and separateeven on computing devices associated with a plurality of communicationchannels.

A communication channel may be “public,” which may allow any clientdevice to join and participate in the information sharing through thecommunication channel. A communication channel may be “private,” whichmay restrict data communications in the communication channel to certainclient devices and/or users.

The term “group-based communication channel interface” refers to avirtual communications environment or feed that is configured to displaymessaging communications posted by channel members (e.g., validatedusers accessing the environment using client devices) that are viewableonly to the members of the group. The format of the group-basedcommunication channel interface may appear differently to differentmembers of the group-based communication channel; however, the contentof the group-based communication channel interface (i.e., messagingcommunications) will be displayed to each member of the group-basedcommunication channel. For instance, a common set of group-basedmessaging communications will be displayed to each member of therespective group-based communication channel such that the content ofthe group-based communication channel interface (i.e., messagingcommunications) will not vary per member of the group-basedcommunication channel.

In certain embodiments, the group-based communication interface maycomprise multiple visible panes within a display window, for example. Incertain embodiments, each display pane may be configured to displayspecific data types. For example, a left-most pane may provide a listingof channels and/or direct messages available to a user and a right-most(or center pane, in a 3-pane configuration) may display the content of aparticular channel in which messages are exchanged, including displayingall of those displayed messages. The content of the center pane may bepresented as a scrollable feed in certain embodiments. In embodiments inwhich the main display window comprises 3-panes, the right-most pane maycomprise additional data regarding a particular selected message,channel, and/or the like.

As used herein, the terms “messaging communication” and “message” referto any electronically generated digital content object provided by auser using a client device and that is configured for display within agroup-based communication interface. Message communications may includeany text, image, video, audio, or combination thereof provided by a user(using a client device). For instance, the user may provide a messagingcommunication that includes text as well as an image and a video withinthe messaging communication as message contents. In such a case, thetext, image, and video would comprise the messaging communication ordigital content object. Each message sent or posted to a communicationchannel (e.g., a group-based communication channel) of the group-basedcommunication system includes metadata comprising the following: asending user identifier, a message identifier, message contents, anobject identifier, a group identifier and/or a group-based communicationchannel identifier. Each of the foregoing identifiers may comprise ASCIItext, a pointer, a memory address, and the like. Messages may begenerated and/or edited within an individual pane of a group-basedcommunication interface (a single pane being visible within a particulardisplay window) and/or messages may be generated and/or edited withinseparate display windows (e.g., separate display windows may be utilizedfor generating postings to be shared within a communication channeland/or for initiating a call with other users).

The term “object” as used herein may refer to any content source forwhich updates may be provided and disseminated to one or more clientdevices. A particular user may be considered an object to other users,such that updates regarding the characteristics and/or activities of theparticular user may be disseminated to other client devices. Objects mayalso be embodied as files in certain embodiments, such that updates tothose files may be disseminated to individual client devices. Objectsmay also be embodied as channels in certain embodiments, such thatupdates to those channels may be disseminated to individual clientdevices. Updates relating to particular objects may be disseminated fromthe group-based communication platform to individual client devices asmessages, which may comprise additional metadata identifying aparticular object (referred to herein as an object identifier) to whichthe updates relate. These object identifiers enable a client device todisplay the update in association with the appropriate object and/orstore the update in association with the appropriate object within alocal data store on the client device. In certain embodiments, theobject identifiers comprise data indicative of the type of object towhich the object relates (e.g., a user object, a file object, and/or thelike) and may additionally or alternatively comprise data indicative ofa unique string (e.g., a unique number, a unique alphanumeric string,and/or the like) that uniquely identifies the object (e.g., among all ofobjects or among all objects of a particular object type). Inembodiments, a group-based communication interface object is associatedwith an object such that a group-based communication interface is arendering in a graphical user interface (GUI) of a representation of theobject.

Object updates (or “updated object data”) may be provided to clientdevices. Objects stored locally within a local data store on the clientdevice (e.g., locally stored copies of objects reflected on thecomputing platform) are updated by replacing and/or supplementing datastored within the local data store of the client device with new datareflective of the object updates received from a computing platform,such as the group-based communication platform. For example, updatedobject data may be representative of events associated with group-basedcommunication interface objects (e.g., channels) to which the clientdevice has subscribed (e.g., a websocket event subscription).

The locally stored objects within the data store may be utilized by oneor more applications, computer programs, or other local processinginstances executing on the client device. These local processinginstances may comprise one or more graphical user interfaces fordisplaying objects, one or more executable programs configured forintaking objects as input, and/or the like. The locally stored objectsmay be retrieved from the local data store via a “get” process in whichthe objects are retrieved from the local data store and passed to one ormore local processing instances. In examples, the locally stored objectsare utilized in generating, for display, a group-based communicationsinterface on a client device.

The terms “group identifier” or “team identifier” refer to one or moreitems of data by which a group within a group-based communication systemmay be identified. For example, a group identifier may comprise ASCIItext, a pointer, a memory address, and the like.

The terms “group-based communication channel identifier” or “channelidentifier” refer to one or more items of data by which a group-basedcommunication channel may be identified. For example, a group-basedcommunication channel identifier may comprise ASCII text, a pointer, amemory address, and the like. In certain embodiments, a communicationchannel (whether public or private) may be available for use betweenusers (and their associated client devices) of a common group/team,although cross-group communication channels may be available betweenclient devices associated with users of separate teams. Thus, a channelidentifier may be provided together with one or more group identifiersto specifically identify where data/messages related to the particularcommunication channel are stored.

The term “group-based communication interface” refers to a virtualcommunications environment configured to facilitate user interactionwith a group-based communications system. Each group-based communicationinterface is accessible and viewable to a selected group of users, suchas a group of employees of a business or organization (e.g., the SlackCorp. interface would be accessible and viewable to the Slack employeeshowever the ACME Corporation group-based communication interface mightnot be accessible and viewable to Slack employees unless the interfaceis designated as shared). The group-based communication interfaceincludes a plurality of group-based communication channels (e.g., amarketing channel, sales channel, accounting channel, etc.), which aredefined below.

A “sending user identifier” is associated with a collection of messagesthat are sent by a particular user (i.e., a client device associatedwith the particular user). These messages may be analyzed to determinecontext regarding the user (e.g., the user's expertise or interest in atopic may be determined based on the frequency of mention of the topicor key words associated with the topic within such messages).

Group-based communication system users are organized into organizationgroups (e.g., employees of each company may be a separate organizationgroup) and each organization group may have one or more communicationchannels (e.g., group-based communication channels) to which users maybe assigned or which the users may join (e.g., group-based communicationchannels may represent departments, geographic locations such asoffices, product lines, user interests, topics, issues, and/or thelike). A group identifier may be used to facilitate access control for amessage (e.g., access to the message, such as having the message returnas part of search results in response to a search query, may berestricted to those users having the group identifier associated withtheir user profile). The group identifier may be used to determinecontext for the message (e.g., a description of the group, such as thename of an organization and/or a brief description of the organization,may be associated with the group identifier).

Group-based communication system users may join and/or createcommunication channels (e.g., group-based communication channels). Somegroup-based communication channels may be globally accessible to thoseusers having a particular organizational group identifier associatedwith their user profile (i.e., users who are members of theorganization). Access to some group-based communication channels may berestricted to members of specified groups, whereby the group-basedcommunication channels are accessible to those users having a particulargroup identifier associated with their user profile. The group-basedcommunication channel identifier may be used to facilitate accesscontrol for a message (e.g., access to the message, such as having themessage return as part of search results in response to a search query,may be restricted to those users having the group-based communicationchannel identifier associated with their user profile, or who have theability to join the group-based communication channel). The group-basedcommunication channel identifier may be used to determine context forthe message (e.g., a description of the group-based communicationchannel, such as a description of a project discussed in the group-basedcommunication channel, may be associated with the group-basedcommunication channel identifier). A group-based communication channelmay have a name associated therewith (a group-based communicationchannel name) that may be displayed in a group-based communicationinterface such that a user having a client device may interact with theinterface in order to select the displayed name.

The term “private group-based communication channel” refers to agroup-based communication channel with restricted access such that it isnot generally accessible and/or searchable by other members of thegroup-based communication system. For example, only those users oradministrators who have knowledge of and permission to access (e.g., agroup-based communication channel identifier for the private group-basedcommunication channel is associated with their user profile after theuser has been validated/authenticated) the private group-basedcommunication channel may view content of the private group-basedcommunication channel.

“Group-based communication servers” or “remote servers” as discussedherein with reference to certain embodiments are computing devicesconfigured for interacting with various client devices (e.g., via aninterface computing entity) for receiving and/or disseminating objectupdates and/or other messages among client devices. Group-basedcommunication servers may be configured to receive, generate, store (inan associated database), and/or direct messages received from and/ordisseminated to users (e.g., via corresponding client devices). Thefunctionality of the group-based communication servers may be providedvia a single server or collection of servers having a commonfunctionality, or the functionality of the group-based communicationservers may be segmented among a plurality of servers or collections ofservers performing subsets of the described functionality of thegroup-based communication servers.

The group-based communication servers or remote servers may beconfigured to maintain connection sessions with various client devices.Specifically, one or more servers may be configured for maintainingwebsocket connections (e.g., active websocket connections) initiated byeach of a plurality of client devices for transmitting messages (e.g.,object updates) and corresponding metadata (e.g., comprising objectidentifiers) in real time between group-based communication servers ofthe group-based communication platform and respective client devices.

The term “server-push-based communications connection” refers to anetwork connection over which a request for transmission of informationis initiated by a server or publisher. In embodiments, a“server-push-based communications connection” may be based oninformation preferences expressed in advance by the client device to theserver. In embodiments, a server-push-based communications connectionmay also be based on information associated with a user identifierassociated with the client device. In embodiments, a client devicesubscribes to events associated with particular object identifiers suchthat whenever updated object data is available for the particular objectidentifier (i.e., an event has occurred), the server pushes the updatedobject data to the client device.

The term “client-pull-based communications connection” refers to anetwork connection over which a request for transmission of informationis initiated by a client device or requester and responded to by aserver or publisher.

The term “real-time” is used to describe a computing application thatresponds as rapidly as required by a user accessing the computingapplication. For example, real-time messaging may comprise group-basedcommunication interfaces that provide a real-time or live transmissionof messages from a sending client device to a receiving client device.It will be appreciated that “real-time” may be considered “without unduedelay,” or “as instantaneously as possible” within computingconstraints.

The term “user interaction input” refers to input received by a clientdevice as a result of user interaction with input devices communicablycoupled to the client device. For example, user interaction input maycomprise mouse-clicks and/or touch screen selections.

The term “electronic interactions” refers to electronic representationsof user interaction inputs. For example, a user interaction in the formof a mouse-click may be represented by a timestamp, an objectidentifier, and an interaction type (e.g., selection/click).

The term “tail data payload” refers to a plurality of data recordsassociated with an object identifier, and associated with timestampsprior to a timestamp associated with a polling request for the tail datapayload. For example, a tail data payload may represent a defined number(e.g., N, 20, etc.) of “recent” object events (e.g., messages,reactions, edits, deletions) associated with an object identifier (e.g.,a group-based communication channel identifier).

The term “interruption” refers to a failure of a network/communicationconnection.

The term “polling request” refers to a message transmitted from a clientdevice to a group-based communication server, the request being forretrieval of data by the client device from the group-basedcommunication server. In examples, a polling request comprises an objectidentifier, a client device identifier, and a timestamp.

The term “tail data payload subset” refers to a subset of data containedin a tail data payload.

The term “updated content identifier” refers to a digital representationof an instance of updated content. For example, an updated contentidentifier may be a timestamp, a monotonically incremented revisionnumber, and an identifier derived from one of content or a content hash.It will be appreciated that the updated content identifier providesindication to a client device that a change to content has occurred.

The term “timestamp” refers to a digital representation of an instancein network time associated with a particular occurrence, such as apolling request or message transmission. For example, a timestamp can bethe following: “<timestamp>2020-12-31 23:59:59</timestamp>”. Inembodiments, a timestamp is in relation to a wall clock (e.g.,2020-12-31). In embodiments, a timestamp is a monotonically increasingidentifier (e.g., one or more items of data by which an instance may beuniquely identified) that supports comparison of changes (i.e., older ornewer changes). In embodiments, a timestamp is a content addressedidentifier (e.g., one or more items of data by which a change in contentmay be uniquely identified) that represents that an instance oroccurrence of content is different from a previous instance oroccurrence.

It will be appreciated that a timestamp in relation to a wall clock anda timestamp that is a monotonically increasing identifier provide aclient device with an indication that data has been updated over time.It will further be appreciated that the timestamp as a content addressedidentifier provides a client device with an indication that data isdifferent over time. It will be appreciated that one or a combination ofall the above described timestamp examples can be used in embodiments ofthe present disclosure at any given time or in any given module.

The term “polling request timestamp” refers to a timestamp associatedwith when a particular polling request was transmitted by a clientdevice or received by a group-based communication server.

The term “record” refers to a data structure containing object dataassociated with a particular object identifier. In embodiments, theobject data is associated with a timestamp. In embodiments, the recordis associated with a timestamp.

The term “mouse-click” refers to an input received by a client devicefrom a hand-held pointing device communicably coupled thereto. Inembodiments, a mouse-click indicates an electronic selection of one of aplurality of displayed objects in a group-based communication interface.In embodiments, a mouse-click is associated with one or more objectidentifiers.

The term “touch screen selection” refers to an input received by aclient device from an input device (e.g., screen) layered on top of anelectronic visual display of the client device. In embodiments, a touchscreen selection indicates a “touch” of the screen where an object ofthe group-based communication interface is displayed. In embodiments, atouch screen selection is associated with one or more objectidentifiers.

The term “web API” refers to a set of defined interfaces through whichinteractions occur between a group-based communication platform andclient or other devices accessing the group-based communicationplatform. In examples, a web API is a set of specifications, such asHypertext Transfer Protocol (HTTP) request messages, and a set ofresponse messages in, for example, JavaScript Object Notation (JSON)format.

The term “HTTP request” refers to an HTTP message transmitted from aclient device to a group-based communication server, the request beingfor retrieval of data by the client device from the group-basedcommunication server. In embodiments, the HTTP request may be a GET orPOST request.

In certain embodiments, one or more of the interface computing entitiesand/or the message distribution servers may be geographicallydistributed, for example, to service client devices locatedgeographically proximate the one or more computing entities. However, incertain embodiments the various computing entities (including theinterface computing entities and/or the message distribution servers)may be centrally-located.

Example System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a network device, such as a server orother network entity, configured to communicate with one or moredevices, such as one or more client devices. In some preferred andnon-limiting embodiments, the computing device may include fixedcomputing devices, such as a personal computer or a computerworkstation. Still further, example embodiments may be embodied by anyof a variety of mobile devices, such as a portable digital assistant(PDA), mobile phone, smartphone, laptop computer, tablet computer,wearable device, or any combination of the aforementioned devices.

FIG. 1 illustrates example computing systems within which embodiments ofthe present invention may operate. Users may access a group-basedcommunication platform 105 via a communication network 104 using clientdevices 101A-101N.

Communication network 104 may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, communication network 104 mayinclude a cellular telephone, an 802.11, 802.16, 802.20, and/or WiMaxnetwork. Further, the communication network 104 may include a publicnetwork, such as the Internet, a private network, such as an intranet,or combinations thereof, and may utilize a variety of networkingprotocols now available or later developed including, but not limited toTCP/IP based networking protocols. As discussed herein, the networkingprotocol is configured to enable data transmission via websocketcommunications. For instance, the networking protocol may be customizedto suit the needs of the group-based communication system. In someembodiments, the protocol is a custom protocol of JSON objects sent viaa websocket channel. In some embodiments, data may be transmitted via aplurality of protocols, such as JSON over RPC, JSON over REST/HTTP, andthe like.

In the illustrated embodiment, the group-based communication platform105 includes a plurality of group-based communication repositories 107and plurality of group-based communication servers 106_1-106N accessiblevia the communication network 103. Collectively, the group-basedcommunication servers 106_1-106N are configured for receiving messagestransmitted from one or more client devices 101A-101N, generating and/orreceiving messages indicative of object updates (if applicable), fortransmitting messages to appropriate client devices 101A-101N.

The client devices 101A-101N may be any computing device as definedabove. Electronic message data exchanged between the group-basedcommunication servers 106_1-106N and the client devices 101A-101N may beprovided in various forms and via various methods.

In some preferred and non-limiting embodiments, one or more of theclient devices 101A-101N are mobile devices, such as smartphones ortablets. The one or more client devices may execute an “app” or otherexecutable local processing instance to interact with the group-basedcommunication servers 106_1-106N. Such apps are typically designed toexecute on mobile devices, such as smartphones or tablets. For example,an app may be provided that executes on mobile device operating systemssuch as iOS®, Android®, or Windows®. These platforms typically provideframeworks that allow apps to communicate with one another, and withparticular hardware and software components of mobile devices. Forexample, the mobile operating systems named above each providesframeworks for interacting with location services circuitry, wired andwireless network interfaces, user contacts, and other applications.Communication with hardware and software modules executing outside ofthe app is typically provided via application programming interfaces(APIs) provided by the mobile device operating system. Thus, via the appexecuting on the client devices 101A-101N, these client devices101A-101N are configured for communicating with the group-basedcommunication platform 105 via one or more websockets or othercommunication connection.

In some preferred and non-limiting embodiments, the client devices101A-101N may interact with the group-based communication servers106_1-106N via a web browser. The client devices 101A-101N may alsoinclude various hardware or firmware designed to interact with thegroup-based communication servers 106_1-106N. Again, via the browser ofthe client devices 101A-101N, the client devices 101A-101N areconfigured for communicating with the group-based communication platform105 via one or more websockets or other communication connection.

In some embodiments of an exemplary group-based communication platform105, a message or messaging communication may be sent from a clientdevice 101A-101N to a group-based communication platform 105. In variousimplementations, messages may be sent to the group-based communicationplatform 105 over communication network 104 directly by one of theclient devices 101A-101N. The messages may be sent to the group-basedcommunication platform 105 via an intermediary such as a message server,and/or the like. For example, a client device 101A-101N may be adesktop, a laptop, a tablet, a smartphone, and/or the like that isexecuting a client application (e.g., a group-based communication app).In one implementation, the message may include data such as a messageidentifier, sending user identifier, a group identifier, a group-basedcommunication channel identifier, message contents (e.g., text, emojis,images, links), attachments (e.g., files), message hierarchy data (e.g.,the message may be a reply to another message), third party metadata,and/or the like. In one embodiment, the client device 101A-101N mayprovide the following example message, substantially in the form of a(Secure) Hypertext Transfer Protocol (“HTTP(S)”) POST message includingeXtensible Markup Language (“XML”) formatted data, as provided below:

-   POST /authrequest.php HTTP/1.1-   Host: www.server.com-   Content-Type: Application/XML-   Content-Length: 667-   <?XML version=“1.0” encoding=“UTF-8”?>-   <auth_request>    -   <timestamp>2020-12-31 23:59:59</timestamp>    -   <user_accounts_details>        -   <user_account_credentials>            -   <user_name>ID_user_1</user_name>            -   <password>abc123</password>            -   //OPTIONAL <cookie>cookieID</cookie>            -   //OPTIONAL                <digital_cert_link>www.mydigitalcertificate.com/                JohnDoeDaDoeDoe@gmail.com/mycertificate.dc</digital_cert_link>            -   //OPTIONAL                <digital_certificate>_DATA_</digital_certificate>        -   </user_accounts_details>    -   </user_accounts_details>    -   <client_details> //iOS Client with App and Webkit        -   //it should be noted that although several client details        -   //sections are provided to show example variants of client        -   //sources, further messages will include only on to save        -   //space        -   <client_IP>10.0.0.123</client_IP>        -   <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1            like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko)            Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string>        -   <client_product_type>iPhone6,1</client_product_type>        -   <client_serial_numbers>DNXXX1X1XXXX</client_serial_number>    -   <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>        -   <client_OS>iOS</client_OS>        -   <client_OS_version>7.1.1</client_OS_version>        -   <client_app_type>app with webkit</client_app_type>        -   <app_installed_flag>true</app_installed_flag>        -   <app_name>MSM.app</app_name>        -   <app_version>1.0</app_version>        -   <app_webkit_name>Mobile Safari</client_webkit_name>        -   <client_version>537.51.2</client_version>    -   </client_details>    -   <client_details> //iOS Client with Webbrowser        -   <client_IP>10.0.0.123</client_IP>        -   <user_agent_string>Mozilla/5.0 (iPhone; CPU iPhone OS 7_1_1            like Mac OS X) AppleWebKit/537.51.2 (KHTML, like Gecko)            Version/7.0 Mobile/11D201 Safari/9537.53</user_agent_string>        -   <client_product_type>iPhone6,1</client_product_type>        -   <client_serial_number>DNXXX1X1XXXX</client_serial_number>    -   <client_UDID>3XXXXXXXXXXXXXXXXXXXXXXXXD</client_UDID>        -   <client_OS>iOS</client_OS>        -   <client_OS_version>7.1.1</client_OS_version>        -   <client_app_type>web browser</client_app_type>        -   <client_name>Mobile Safari</client_name>        -   <client_version>9537.53</client_version>    -   </client_details>    -   <client_details> //Android Client with Webbrowser        -   <client_IP>10.0.0.123</client_IP>        -   <user_agent_string>Mozilla/5.0 (Linux; U; Android 4.0.4;            en-us; Nexus S Build/IMM76D) AppleWebKit/534.30 (KHTML, like            Gecko) Version/4.0 Mobile Safari/534.30</user_agent_string>        -   <client_product_type>Nexus S</client_product_type>        -   <client_serial_number>YXXXXXXXXZ</client_serial_number>        -   <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXX</client_UDID>        -   <client_OS>Android</client_OS>        -   <client_OS_version>4.0.4</client_OS_version>        -   <client_app_type>web browser</client_app_type>        -   <client_name>Mobile Safari</client_name>        -   <client_version>534.30</client_version>    -   </client_details>    -   <client_details>//Mac Desktop with Webbrowser        -   <client_IP>10.0.0.123</client_IP>        -   <user_agent_string>Mozilla/5.0 (Macintosh; Intel Mac OS X            10_9_3) AppleWebKit/537.75.14 (KHTML, like Gecko)            Version/7.0.3 Safari/537.75.14</user_agent_string>        -   <client_product_type>MacPro5,1</client_product_type>        -   <client_serial_number>YXXXXXXXXZ</client_serial_number>        -   <client_UDID>FXXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXX</client_UDID>        -   <client_OS>Mac OS X</client_OS>        -   <client_OS_version>10.9.3</client_OS_version>        -   <client_app_type>web browser</client_app_type>        -   <client_name>Mobile Safari</client_name>        -   <client_version>537.75.14</client_version>    -   </client_details>    -   <message>        -   <message_identifier>ID_message_10</message_identifier>        -   <team_identifier>ID_team_1</team_identifier>        -   <channel_identifier>ID_channel_1</channel_identifier>        -   <contents>That is an interesting invention. I have attached            a copy our patent policy.</contents>        -   <attachments>patent_policy.pdf</attachments>    -   </message>-   </auth_request>

In the illustrated embodiment, the group-based communication platform105 comprises a plurality of group-based communication servers106_1-106N configured to receive and/or disseminate messages transmittedbetween and/or to a plurality of client devices 101A-101N within achannel identified by a channel identifier and/or a group identifier,and to facilitate dissemination of those messages among client devices101A-101N that collectively form the membership of the communicationchannel.

In some embodiments, an object identifier as defined above may beassociated with the message to indicate that a particular message isembodied as an object update relating to a particular object.

In some embodiments, data indicating responses may be associated withthe message. For example, responses to the message by other users mayinclude reactions (e.g., selection of an emoji associated with themessage, selection of a “like” button associated with the message),clicking on a hyperlink embedded in the message, replying to the message(e.g., posting a message to the group-based communication channelinterface in response to the message), downloading a file associatedwith the message, sharing the message from one group-based communicationchannel to another group-based communication channel, pinning themessage, starring the message, and/or the like. In one implementation,data regarding responses to the message by other users may be includedwith the message, and the message may be parsed (e.g., using PHPcommands) to determine the responses. In another implementation, dataregarding responses to the message may be retrieved from a database. Forexample, data regarding responses to the message may be retrieved via aMySQL database command similar to the following:

-   SELECT messageResponses-   FROM MSM_Message-   WHERE messageID=ID_message_10.

For example, data regarding responses to the message may be used todetermine context for the message (e.g., a social score for the messagefrom the perspective of some user). In another example, data regardingresponses to the message may be analyzed to determine context regardingthe user (e.g., the user's expertise in a topic may be determined basedon the responses to the user's message regarding the topic).

In embodiments, attachments may be included with the message. If thereare attachments, files may be associated with the message, and thesefiles may be separately identified as objects having a correspondingobject identifier in certain embodiments. In one implementation, themessage may be parsed (e.g., using PHP commands) to determine file namesof the attachments. For example, file contents may be analyzed todetermine context for the message (e.g., a patent policy document mayindicate that the message is associated with the topic “patents”).

In embodiments, a conversation primitive may be associated with themessage. In one implementation, a conversation primitive is an elementused to analyze, index, store, and/or the like messages. For example,the message may be analyzed by itself, and may form its own conversationprimitive. In another example, the message may be analyzed along withother messages that make up a conversation, and the messages that makeup the conversation may form a conversation primitive. In oneimplementation, the conversation primitive may be determined as themessage, a specified number (e.g., two) of preceding messages and aspecified number (e.g., two) of following messages. In anotherimplementation, the conversation primitive may be determined based onanalysis of topics discussed in the message and other messages (e.g., inthe channel) and/or proximity (e.g., message send order proximity,message send time proximity) of these messages.

In embodiments, various metadata, determined as described above, and/orthe contents of the message may be used to index the message (e.g.,using the conversation primitive) and/or to facilitate various facets ofsearching (i.e., search queries that return results from the group-basedcommunication servers 106_1-106N). Metadata associated with the messagemay be determined and the message may be indexed in the group-basedcommunication servers 106_1-106N. In one embodiment, the message may beindexed such that a company's or a group's messages are indexedseparately (e.g., in a separate index associated with the group and/orcompany that is not shared with other groups and/or companies). In oneimplementation, messages may be indexed at a separate distributedrepository (e.g., to facilitate data isolation for security purposes).If there are attachments associated with the message, file contents ofthe associated files may be used to index such files in the group-basedcommunication servers 106_1-106N to facilitate searching. In oneembodiment, the files may be indexed such that a company's or a group'sfiles are indexed at a separate distributed repository.

Examples of electronic information exchange among one or more clientdevices 101A-101N and the group-based communication platform 105 aredescribed below with reference to FIG. 1 .

As shown in FIG. 1 , the group-based communication platform 105 enablesindividual client devices 101A-101N to exchange various messages withone another and/or to retrieve object updates disseminated from thegroup-based communication platform 105. To exchange such messages,individual client devices 101A-101N transmit messages (e.g., text-basedmessages, files, video and/or audio streams, and/or the like) via acommunication protocol (e.g., via a websocket, a non-RTM (non-Real TimeMessaging) messaging protocol, and/or the like). Those messages areultimately provided to one or more group-based communication servers106_1-106N, which indexes the messages and distributes those messages tothe intended recipients (e.g., client devices 101A-101N) of the message.Object updates are similarly provided to the group-based communicationservers 106_1-106N, however such object updates may not originate fromclient devices 101A-101N. Instead, object updates may be provided fromone or more external systems (e.g., file management systems) or theobject updates may be generated by one or more computing entities withinthe group-based communication platform 105. The distributed messages areprovided to the recipient client devices 101A-101N via the group-basedcommunication servers 106_1-106N, which maintain websocket connectionswith individual recipient client devices 101A-101N of the message.

According to the embodiment of FIG. 1 , the client devices 101A-101N areconfigured to display the received message in contextually-relevant userinterfaces available to the user of the client device 101A-101N. Forexample, messages transmitted from a first client device 101 as a partof a group-based communication channel are displayed in a user interfacedisplay window on client devices 101A-101N associated with other membersof the group-based communication channel. As discussed herein, messagesindicative of particular object updates are transmitted with objectidentifiers usable by the recipient client devices 101A-101N to displaythose messages with appropriate context, such as appropriate userdisplay elements and/or in association with applicable objects.Moreover, the object identifiers may be usable by various ones of thegroup-based communication servers 106_1-106N to filter messages destinedfor particular client devices 101A-101N based on object subscriptions asdiscussed herein.

To distribute messages to individual client devices 101A-101N, themessages are transmitted from the group-based communication servers106_1-106N, which direct all messages destined for respective ones ofthe client devices 101A-101N, and transmits all of those messages to theclient devices 101A-101N over appropriate connections (e.g., websocketconnections, or non-RTM connections).

Example Apparatuses Utilized with Various Embodiments

Each group-based communication server 106 may be embodied by one or morecomputing systems, such as apparatus 200 shown in FIG. 2A. The apparatus200 may include processor 202, memory 204, input/output circuitry 206,communications circuitry 208, and group-based communication circuitry210. The apparatus 200 may be configured to execute the operationsdescribed herein. Although these components 202-210 are described withrespect to functional limitations, it should be understood that theparticular implementations necessarily include the use of particularhardware. It should also be understood that certain of these components202-210 may include similar or common hardware. For example, two sets ofcircuitries may both leverage use of the same processor, networkinterface, storage medium, or the like to perform their associatedfunctions, such that duplicate hardware is not required for each set ofcircuitries.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 204 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 202 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 202 may beconfigured to execute instructions stored in the memory 204 or otherwiseaccessible to the processor 202. In some preferred and non-limitingembodiments, the processor 202 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 202 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 202 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 202 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

As just one example, the processor 202 may be configured to maintain oneor more communication channels connecting a plurality of client devices101A-101N to enable message sharing/dissemination therebetween. Theprocessor 202 ensures that messages intended for exchange between theclient devices 101A-101N within the particular communication channel areproperly disseminated to those client devices 101A-101N for displaywithin respective display windows provided via the client devices101A-101N.

Moreover, the processor 202 may be configured to synchronize messagesexchanged on a particular communication channel with a database forstorage and/or indexing of messages therein. In certain embodiments, theprocessor 202 may provide stored and/or indexed messages to theinterface computing entity 109 for dissemination to client devices101A-101N.

In some embodiments, the apparatus 200 may include input/outputcircuitry 206 that may, in turn, be in communication with processor 202to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 206 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 206 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms. The processorand/or user interface circuitry comprising the processor may beconfigured to control one or more functions of one or more userinterface elements through computer program instructions (e.g., softwareand/or firmware) stored on a memory accessible to the processor (e.g.,memory 204, and/or the like).

The communications circuitry 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communications circuitry 208may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 208 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 208 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

Group-based communication circuitry 210 includes hardware configured toreceive and distribute electronic messages and associated metadatareceived from one or more client devices 101A-101N to other clientdevices 101A-101N based on database shard(s). The group-basedcommunication circuitry 210 may utilize processing circuitry, such asthe processor 202, to perform these actions. However, it should also beappreciated that, in some embodiments, the group-based communicationcircuitry 210 may include a separate processor, specially configuredField Programmable Gate Array (FPGA), or Application Specific IntegratedCircuit (ASIC) for performing the functions described herein. Thegroup-based communication circuitry 210 may be implemented usinghardware components of the apparatus configured by either hardware orsoftware for implementing these planned functions.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 200. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

In the illustrated embodiment of FIG. 2B, the client device 101 isembodied by one or more computing systems encompassing apparatus 220.The illustrated apparatus 220 includes processor 212, memory 211,input/output circuitry 213, and communications circuitry 215. Theapparatus 220 may be configured to execute the operations describedherein. Although these components 211, 212, 213, 215 are described withrespect to functional limitations, it should be understood that theparticular implementations necessarily include the use of particularhardware. It should also be understood that certain of these components211, 212, 213, 215 may include similar or common hardware. For example,two sets of circuitries may both leverage use of the same processor,network interface, storage medium, or the like to perform theirassociated functions, such that duplicate hardware is not required foreach set of circuitries.

In some embodiments, the processor 212 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 211 via a bus forpassing information among components of the apparatus. The memory 211 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 211 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 211 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus 220 to carry out various functions in accordance with exampleembodiments of the present invention. For example, the memory 211 may beconfigured to cache messages exchanged on one or more group-basedcommunication channels, such that the processor 212 may provide variousmessages to client devices (e.g., on an as needed or as requestedbasis).

The processor 212 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 212 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading.

In some preferred and non-limiting embodiments, the processor 212 may beconfigured to execute instructions stored in the memory 211 or otherwiseaccessible to the processor 212. In some preferred and non-limitingembodiments, the processor 212 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 212 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 212 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 212 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 220 may include input/outputcircuitry 305 that may, in turn, be in communication with processor 212to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 213 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a client device, a kiosk, or the like.In some embodiments, the input/output circuitry 213 may also include akeyboard, a mouse, a joystick, a touch screen, touch areas, soft keys, amicrophone, a speaker, or other input/output mechanisms.

The communications circuitry 215 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 220. In this regard, the communications circuitry 215may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 215 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 215 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 220. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

The term “circuitry” should be understood broadly to include hardwareand, in some embodiments, software for configuring the hardware. Withrespect to components of each apparatus 200, 220, the term “circuitry”as used herein should therefore be understood to include particularhardware configured to perform the functions associated with theparticular circuitry as described herein. For example, in someembodiments, “circuitry” may include processing circuitry, storagemedia, network interfaces, input/output devices, and the like. In someembodiments, other elements of the apparatus 200 may provide orsupplement the functionality of particular circuitry. For example, theprocessor 202 may provide processing functionality, the memory 204 mayprovide storage functionality, the communications circuitry 208 mayprovide network interface functionality, and the like. Similarly, otherelements of the apparatus 220 may provide or supplement thefunctionality of particular circuitry. For example, the processor 212may provide processing functionality, the memory 211 may provide storagefunctionality, the communications circuitry 215 may provide networkinterface functionality, and the like.

As will be appreciated, any such computer program instructions and/orother type of code may be loaded onto a computer, processor or otherprogrammable apparatus's circuitry to produce a machine, such that thecomputer, processor or other programmable circuitry that execute thecode on the machine creates the means for implementing variousfunctions, including those described herein.

As described above and as will be appreciated based on this disclosure,embodiments of the present invention may be configured as methods,mobile devices, backend network devices, and the like. Accordingly,embodiments may comprise various means including entirely of hardware orany combination of software and hardware. Furthermore, embodiments maytake the form of a computer program product on at least onenon-transitory computer-readable storage medium having computer-readableprogram instructions (e.g., computer software) embodied in the storagemedium. Any suitable computer-readable storage medium may be utilizedincluding non-transitory hard disks, CD-ROMs, flash memory, opticalstorage devices, or magnetic storage devices.

Moreover, although not shown, various embodiments of a group-basedcommunication platform may comprise one or more databases configured forstoring and/or indexing messages exchanged within various group-basedcommunication channels.

Example Data Flows

FIGS. 3A and 3B illustrate an exemplary data flow for providing ormaintaining near real-time updated object data within a group-basedcommunication system, according to embodiments of the presentdisclosure.

In embodiments, the client device receives user interaction input 301representative of electronic interactions with group-based communicationinterface objects. In embodiments, the electronic interactions with thegroup-based communication interface objects require updated object datafor rendering a subsequent group-based communications interface. Inembodiments, the electronic interactions are associated with one or moreobject identifiers.

In embodiments, a client device (e.g., 101A-101N) establishes 302 afirst communications connection (e.g., an active websocket connection)with a first remote server (e.g., a group-based communication serverconfigured for real-time messaging communication). In embodiments, thefirst remote server is configured for transmitting in real-time updatedobject data representative of events associated with group-basedcommunication interface objects to which the client device hassubscribed. In embodiments, the updated object data is pushed from thefirst remote server to the client device.

In embodiments, the client device establishes 303 a secondcommunications connection (e.g., non-RTM) with a second remote server(e.g., a group-based communication server not configured for real-timemessaging communications). In embodiments, the second communicationsconnection is a client-pull-based communications connection and isconfigured for requesting and receiving, by the client device, tail datapayloads from the second remote server.

In embodiments, the client device transmits 304 a polling request to thesecond remote server, the polling request comprising the one or moreobject identifiers. In embodiments, the polling request isrepresentative of a request (e.g., HTTP GET) for a tail data payload foreach of the one or more object identifiers.

In embodiments, the client device receives 305 the requested tail datapayloads.

In embodiments, the client device queries 306 a local data store of theclient device for updated object data associated with the one or moreobject identifiers. In the event that updated object data associatedwith the one or more object identifiers is available in the local datastore or has been received from the first remote server, the clientdevice discards the tail data payload.

Upon determining that the updated object data is not available in thelocal data store and/or determining that the updated object data has notbeen received from the first remote server, the client device detects307 an interruption in the first communication connection.

In embodiments, the client device then renders 308 for display thesubsequent group-based communications interface using a tail datapayload subset. In embodiments, the tail data payload subset is selectedfrom the tail data payload based on the required updated object dataassociated with the electronic interactions. In so doing, the subsequentgroup-based communications interface provides a minimum level of serviceand data freshness during an outage or interruption of the firstcommunications connection.

In embodiments, a second tail data payload subset of the tail datapayload is utilized to render for display in the subsequent group-basedcommunications interface a set of updated object data associated withupdated content identifiers.

In embodiments, the tail data payload for each object identifiercomprises an updated object data set having N records, each recordhaving an updated content identifier indicating the record was createdprior to a polling request timestamp associated with the pollingrequest. In such embodiments, the tail data payload represents the Nmost recent updates to objects associated with the object identifier(e.g., the 50 most recent messages posted to a channel; the 10 mostrecent reactions to a message, and the like).

In embodiments, the first communications connection is an activewebsocket connection.

In embodiments, the one or more object identifiers are group-basedcommunication channel identifiers.

In embodiments, an electronic interaction is a selection of a displayedgroup-based communication channel name. For example, an electronicinteraction with an area of a group-based communication interface isassociated with a group-based communication channel identifier. In suchan example, the area may comprise a digital display of text representingthe group-based communication channel name.

In embodiments, the selection of the displayed group-based communicationchannel name is received via one of a mouse-click or a touch screenselection.

In embodiments, the polling request is a transmission of a requestmessage to a web Application Programming Interface (API).

In embodiments, the request message is a Hypertext Transfer Protocol(HTTP) request. In embodiments, the HTTP request may be a GET or POSTrequest.

In embodiments, an updated content identifier comprises one or more of atimestamp, a monotonically incremented revision number, and anidentifier derived from one of content or a content hash.

Conclusion

Many modifications and other embodiments will come to mind to oneskilled in the art to which this disclosure pertains having the benefitof the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that thedisclosure is not to be limited to the specific embodiments disclosedand that modifications and other embodiments are intended to be includedwithin the scope of the appended claims. Although specific terms areemployed herein, they are used in a generic and descriptive sense onlyand not for purposes of limitation.

What is claimed is:
 1. A method of providing near real-time interfacefunctionality to a group-based communication system when it isdetermined that a real-time messaging communications connection isinterrupted, the method comprising: receiving, from a first remoteserver and by a client device, real-time updated object data for thegroup-based communication system; transmitting, by the client device toa second remote server, client-pull-based requests; receiving, by theclient device from the second remote server, a tail data payload foreach of one or more object identifiers; and in response to detecting aninterruption in the real-time messaging communications connection,rendering a subsequent group-based communications interface on theclient device using at least a portion of the tail data payloads.
 2. Themethod of claim 1, wherein the subsequent group-based communicationinterface is rendered for display using a first tail data payload subsetselected from the tail data payload based on the updated object data. 3.The method of claim 2, further comprising: rendering for display,utilizing a second tail data payload subset, in the subsequentgroup-based communications interface, a set of updated object dataassociated with updated content identifiers.
 4. The method of claim 3,wherein the subsequent group-based communications interface is based ona user interaction with group-based communication interface objects,wherein the group-based communication interface objects are indicativeof a group-based communication channel.
 5. The method of claim 1,further comprising: transmitting a polling request to the second remoteserver, wherein the polling request comprises the one or more objectidentifiers.
 6. The method of claim 5, wherein the polling requestfurther comprises a client device identifier and a timestamp.
 7. Themethod of claim 6, wherein the tail data payload for each of the one ormore object identifiers comprises an updated object data set including Nmost recent records, and wherein each of the most recent recordsincludes an updated content identifier indicating that each of the mostrecent records were created prior to the timestamp.
 8. One or morenon-transitory computer-readable media storing computer-executableinstructions that, when executed by a processor, perform a method ofproviding near real-time interface functionality to a group-basedcommunication system when it is determined that a real-time messagingcommunication connection is interrupted, the method comprising:receiving, from a first remote server and by a client device, real-timeupdated object data for the group-based communication system;transmitting, by the client device to a second remote server,client-pull-based requests; receiving, by the client device from thesecond remote server, a tail data payload for each of one or more objectidentifiers; and in response to detecting an interruption in thereal-time messaging communication connection, rendering a subsequentgroup-based communications interface on the client device using at leasta portion of the tail data payloads.
 9. The media of claim 8, whereinthe subsequent group-based communication interface is rendered fordisplay using a first tail data payload subset selected from the taildata payload based on the updated object data.
 10. The media of claim 9,wherein the computer-executable instructions are further configured toperform rendering for display, utilizing a second tail data payloadsubset, in the subsequent group-based communications interface, a set ofupdated object data associated with updated content identifiers.
 11. Themedia of claim 10, wherein the subsequent group-based communicationsinterface is based on a user interaction with a group-basedcommunication interface object, wherein the group-based communicationinterface object is indicative of a group-based communication channel.12. The media of claim 8, wherein the computer-executable instructionsare further configured to perform transmitting a polling request to thesecond remote server, wherein the polling request comprises the one ormore object identifiers.
 13. The media of claim 12, wherein the pollingrequest further comprises a client device identifier and a timestamp,wherein the tail data payload for each of the one or more objectidentifiers comprises an updated object data set including N most recentrecords, and wherein each of the most recent records includes an updatedcontent identifier indicating each of the most recent records wascreated prior to the timestamp.
 14. The media of claim 13, wherein theupdated content identifier comprises one or more of an updatedtimestamp, a monotonically incremented revision number, and anidentifier derived from one or content or a content hash.
 15. A systemfor providing a real-time interface when a real-time messagingcommunication connection is interrupted, the system comprising: amemory; a processor; and one or more non-transitory computer-readablemedia storing computer-executable instructions that, when executed bythe processor, perform a method of providing near real-time interfacefunctionality to a group-based communication system when it isdetermined that a real-time messaging communications connection isinterrupted, the method comprising: receiving, from a first remoteserver and by a client device, real-time updated object data for thegroup-based communication system; transmitting, by the client device toa second remote server, client-pull-based requests; receiving, by theclient device from the second remote server, a tail data payload foreach of one or more object identifiers; and in response to detecting aninterruption in the real-time messaging communications connection,rendering a subsequent group-based communications interface on theclient device using at least a portion of the tail data payloads. 16.The system of claim 15, wherein the subsequent group-based communicationinterface is rendered for display using a first tail data payload subsetselected from the tail data payload based on the updated object data.17. The system of claim 16, wherein the computer-executable instructionsare further configured to perform rendering for display, utilizing asecond tail data payload subset, in the subsequent group-basedcommunications interface, a set of updated object data associated withupdated content identifiers.
 18. The system of claim 17, wherein thesubsequent group-based communications interface is based on a userinteraction with a group-based communication interface object, whereinthe group-based communication interface object is indicative of agroup-based communication channel.
 19. The system of claim 18, whereinthe computer-executable instructions are further configured to performthe step of transmitting a polling request to the second remote server,and wherein the polling request comprises the one or more objectidentifiers.
 20. The system of claim 19, wherein the polling requestfurther comprises a client device identifier and a timestamp, whereinthe tail data payload for each of the one or more object identifierscomprises an updated object data set including N most recent records,wherein each of the most recent records includes an updated contentidentifier indicating each of the most recent records was created priorto the timestamp, and wherein the updated content identifier comprisesone or more of an updated timestamp, a monotonically incrementedrevision number, and an identifier derived from one or content or acontent hash.